IBIS Macromodel Task Group Meeting date: 08 November 2022 Members (asterisk for those attending): Achronix Semiconductor: Hansel Dsilva Amazon: John Yan ANSYS: * Curtis Clark Wei-hsing Huang Aurora Systems: * Dian Yang Cadence Design Systems: Ambrish Varma Jared James Google: Hanfeng Wang GaWon Kim Intel: Michael Mirmak * Kinger Cai Chi-te Chen Alaeddin Aydiner Keysight Technologies: * Fangyi Rao Majid Ahadi Dolatsara Ming Yan Radek Biernacki Rui Yang Luminous Computing David Banas Marvell Steve Parker Mathworks (SiSoft): * Walter Katz Mike LaBonte Micron Technology: * Randy Wolff Justin Butterfield Missouri S&T Chulsoon Hwang Yifan Ding Rivos Yansheng Wang SAE ITC Michael McNair Siemens EDA (Mentor): * Arpad Muranyi Teraspeed Labs: * Bob Ross Waymo: Zhiping Yang Zuken USA: * Lance Wang The meeting was led by Arpad Muranyi. Curtis Clark took the minutes. -------------------------------------------------------------------------------- Opens: - Dian Yang from Aurora Systems introduced himself. He is interested in IBIS ATM because his company develops a cloud-based platform for SI and PI simulation. ------------- Review of ARs: - None. -------------------------- Call for patent disclosure: - None. ------------------------- Review of Meeting Minutes: Arpad asked for any comments or corrections to the minutes of the November 1st meeting. Randy moved to approve the minutes. Lance seconded the motion. There were no objections. -------------- New Discussion: clock_times clarification BIRD draft: Arpad shared the latest draft. He noted that he had added the phrase "without altering it in anyway" in order to clarify that the EDA tool should pass the DQS (clock) output to the DQ (data) model unchanged. He also noted that Ambrish had had proposed combining separate "Wave" and "Times" sentences into a single sentence. Randy and Walter said Ambrish's combined sentence was fine. Fangyi suggested we should say "clock signal" instead of just "clock" in this sentence: "... the Clock shall have an AMI executable model with an AMI_GetWave ..." Arpad agreed and said he had considered "clock channel" since we are talking about the simulation and not the model itself, and "Clock" alone is ambiguous. The group discussed this language, but Fangyi said it was a minor point. No changes were made in the draft, though this may be something for the Editorial task group to consider. Walter said that some of the language discussing the DQS model's AMI_GetWave returning a waveform in the "Wave" case was unnecessary. He said it always returns a waveform. Walter made the point that if the DQ model allows "Times" and "Wave" as valid settings of the Rx_Use_Clock_Input, then the corresponding DQS model must always return clock_times and wave. He said the DQS model doesn't know what setting is being used for the DQ model, so it always has to return both the waveform and clock times. The group made some minor edits in this area, but Randy noted that the Usage Rules section for Rx_Use_Clock_Input already describes the outputs of the Clock (DQS) model. Arpad asked if this was finally in a state to be submitted to the Open Forum. Randy moved to submit this draft to the Open Forum as an official BIRD. Fangyi seconded. There were no objections. (Note: this was submitted and assigned BIRD222). Standard Power Integrity Model (SPIM) BIRD draft: Kinger reviewed draft4 of the proposal, which he had sent to ATM several weeks earlier. He noted that most of it had been reviewed in ATM in previous meetings (see minutes from August 30, 2022, and September 27, 2022). He said he had worked on incorporating the feedback he had received from several people, particularly Bob Ross. Kinger reviewed some of the important changes. He noted that Bob had suggested the [Chip SPIM Group] keyword as selector analogous to [Model Selector]. They had also introduced [SPIM Pin Cluster] to avoid confusion with "group" keyword names. It is used to specify power pin and local ground reference groupings for the ports. [SPIM Current] uses traditional typ/min/max syntax, but the meaning of each is explicitly defined. The typ value is required and defines the thermal design current. The max value is optional but strongly recommended and provides the maximum DC current for use in IR drop calculations. The min value is optional and used to provide the leakage current. Arpad and Bob noted that usage of File_IBIS-ISS in this BIRD will need to include a subcircuit specifier as well as the IBIS-ISS filename, as is done in existing keywords that utilize IBIS-ISS files. Arpad encouraged everyone to review Kinger's draft4 and provide feedback. - Randy: Motion to adjourn. - Kinger: Second. - Arpad: Thank you all for joining. AR: Arpad to submit the latest clock_times clarification BIRD draft to the IBIS Open Forum as an official BIRD. ------------- Next meeting: 15 November 2022 12:00pm PT ------------- IBIS Interconnect SPICE Wish List: 1) Simulator directives